Chrome Installation via Chrome Browser Cloud Management

Use Google Admin to deploy the extension to managed Chrome browsers across Windows, macOS, and Linux.

1. Sign in to Google Admin with a super admin and open: https://admin.google.com/ac/chrome/apps/user
2. Select the organizational unit (OU) to target (or keep the top‑level domain to deploy to all users).
3. Open the Users & browsers tab and click the + button (bottom right).
4. Choose Add Chrome app or extension by ID.
5. Enter the extension ID based on your Sensor version and deployment method:
   • Self‑hosted (Sensor 25.04+): use the self‑hosted extension ID from prerequisites
   • Chrome Web Store: use the store extension ID from prerequisites
6. Update URL:
   • Self‑hosted (Sensor 25.04+): from the drop‑down, select “From a custom URL”, then enter your tenant Chromium update URL (see prerequisites), and Save.
   • Chrome Web Store (earlier sensors): use the store default (no custom URL). If your console requires an explicit URL, use https://clients2.google.com/service/update2/crx.
7. Confirm the Cyberhaven security extension appears in the Apps table for the OU.
8. Set Installation policy to Force install.
9. Set Permissions and URL access to Allow all permissions.
10. Under Deployment settings, set Update URL to Installation URL so Chrome checks the installation URL for updates.
11. Click Save. The extension deploys on the next managed‑browser policy check‑in.

Validation

• On an endpoint, open Chrome and visit chrome://policy/.
• Verify the presence of ExtensionInstallForcelist and ExtensionSettings policies with the Cyberhaven extension ID, Source=Cloud, Level=Mandatory.

Cleanup for macOS MDM

• After confirming Google Admin deployment, you may remove the com.google.Chrome Application payload from the Cyberhaven mobileconfig to avoid policy conflicts. If using Jamf, delete the Chrome policy section matching your deployment method (self‑hosted vs. store) from the imported profile.